<HTML><HEAD><TITLE>EplexInstance:eplex_write(++Format,++File)</TITLE>
</HEAD><BODY>[ <A HREF="index.html">library(eplex)</A> | <A HREF="../../index.html">Reference Manual</A> | <A HREF="../../fullindex.html">Alphabetic Index</A> ]
<H1>EplexInstance:eplex_write(++Format,++File)</H1>
Write the problem in the solver for eplex instance  EplexInstance to a file.
<DL>
<DT><EM>Format</EM></DT>
<DD>lp or mps
</DD>
<DT><EM>File</EM></DT>
<DD>File name
</DD>
</DL>
<H2>Description</H2>

   Write the problem in the solver for EplexInstance to a file. The set of
   supported formats depends on the actual external solver which is used.
   All solvers support the mps format. Some solvers on some operating
   system platforms may change or append a suffix to the filename. 
   Note that the mps format does not specify the sense (min or max) of the
   objective function. Minimisation is also assumed for external solvers
   that ignore the optimisation direction of the lp file (e.g. Xpress).
   Note also that any active cutpool constraints in the problem will be 
   included in the dump, even though they could be left out of the problem
   that the external solver actually solves.

<H3>Exceptions</H3>
<DL>
<DT><EM>(5) type error </EM>
<DD>EplexInstance does not a solver setup for it.
<DT><EM>(40) stale object handle </EM>
<DD>Solver state had been previously destroyed.
</DL>
<H2>See Also</H2>
<A HREF="../../lib/eplex/eplex_read-2.html">eplex_read / 2</A>, <A HREF="../../lib/eplex/lp_write-3.html">lp_write / 3</A>, <A HREF="../../lib/eplex/lp_setup-4.html">lp_setup / 4</A>
</BODY></HTML>
